Skip to content

Drop the "Oklo" release codename and use Gentoo's branding.eclass#3750

Open
chewi wants to merge 4 commits intomainfrom
branding
Open

Drop the "Oklo" release codename and use Gentoo's branding.eclass#3750
chewi wants to merge 4 commits intomainfrom
branding

Conversation

@chewi
Copy link
Contributor

@chewi chewi commented Feb 23, 2026

Drop the "Oklo" and use Gentoo's branding.eclass

The release codename was never updated in a meaningful way. It was only used directly in lsb_release, which is a dead standard. It was included in the os-release PRETTY_NAME but not as a field on its own.

Setting the os-release fields in the profile allows them to be used by the new branding.eclass, which is now applied to various packages, particularly GNU ones.

Since originally preparing the commit, these fields were added to our make.conf, but setting them in the profile is more versatile, allowing for downstreams.

This also drops some dead files.

How to use

ls --help | fgrep -i flatcar

Testing done

I tested this a while ago, but I'll give it a fresh look.

  • Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
  • Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

As far as I can tell, this has never been used.

Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
It was never updated in a meaningful way. It was only used directly in
lsb_release, which is a dead standard. It was included in the os-release
`PRETTY_NAME` but not as a field on its own.

Closes: #88
Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
@chewi chewi self-assigned this Feb 23, 2026
@chewi chewi requested a review from a team as a code owner February 23, 2026 10:35
This leverages the branding eclass that was recently added to Gentoo.

Since originally preparing this commit, these fields were added to our
make.conf, but setting them in the profile is more versatile, allowing
for downstreams.

Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
These have probably have been broken for years.

Signed-off-by: James Le Cuirot <jlecuirot@microsoft.com>
Comment on lines +46 to +53
NAME="$BRANDING_OS_NAME"
ID="$BRANDING_OS_ID"
ID_LIKE="$BRANDING_OS_ID_LIKE"
VERSION="$FLATCAR_VERSION"
VERSION_ID="$FLATCAR_VERSION_ID"
BUILD_ID="$FLATCAR_BUILD_ID"
SYSEXT_LEVEL="1.0"
PRETTY_NAME="$BRANDING_OS_PRETTY_NAME"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was wondering if we could do NAME=${BRANDING_OS_NAME@Q} instead. That would make sure that quoting is done correctly. On the other hand, that probably would break some things because I'm sure that there is some script out there parsing the file and assuming that there are either no quotes or only double quotes. ${BRANDING_OS_NAME@Q} would result in using single quotes, I think.

Anyway, doesn't matter, it's not like we are going to put strange characters here anyway.

[ -d "$ROOT_FS_DIR" ] || die "Root FS does not exist? ($ROOT_FS_DIR)"

OS_NAME="Flatcar Container Linux by Kinvolk"
OS_CODENAME="Oklo"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This must stay. It's not negotiable. Oklo Inc. promised me a nuclear reactor if we keep it.

;)

BRANDING_OS_ID="flatcar"
BRANDING_OS_ID_LIKE="coreos"
BRANDING_OS_HOME_URL="https://flatcar.org"
BRANDING_OS_SUPPORT_URL="https://groups.google.com/forum/#!forum/flatcar-linux-user"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose SUPPORT_URL is not used, yes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants